I worry because I’ve been around this business long enough to remember multiple times when the focus shifted to rapid development instead of custom development, and every time that happened, solution quality suffered
3 Comments - no search term matches found in comments.
SOA benefits include: Reuse – once the service is written it can be plugged in wherever needed versus writing the same application over and over again every time/place you need it Consistency – the service executes the same way every time so, for example, calculations such as APR (a tricky calculation for mortgages and one that has to be correct per compliance guidelines) and underwriting decisions are consistent across applications that consume the service Scalability & Reliability - because the services run in a web server environment they can take advantage of load balancing and fault tolerance technologies to provide scalability and reliability Rapid development – several services can be combined very rapidly to create robust applications without having to write anything but the code necessary to glue them together Integration – access to line of business systems’ data and functionality becomes trivial if these systems are fronted by services The major difficulties of implementing a SOA were/are: Cooperation and consensus between service providers (departments within an organization or separate organizations) on what the service should and should not do, as well as support, Service Level Agreements and security concerns Performance - services tend to carry some overhead versus direct and local function calls Versioning – results returned from a particular service may differ over time as changes are made to the underlying implementation
1 Comment - no search term matches found in comments.